Activity: 08.04 - Test Release
Once the release is successfully compiled, it must undergo different levels of testing before final deployment into production. Back out procedures must also be tested, and a formal sign-off must be obtained from the Client on the Release Test Results.
DescriptionWork Breakdown StructureRolesWork Product Usage
Relationships
Parent Activities
Description

Once the Release Package is compiled and various test environments are established, the Release Package must undergo different levels of testing (as planned in the Test strategy) The Test Team must adhere to the approved test plan and test scenarios and document the test results to the agreed defect categories as planned. The Release Manager must be informed about the exceptions for resolution/escalation/work-arounds. Test scenarios and test results must be documented and shared with all relevant stakeholders. Risks and issues identified as part of the testing process should be captured along with the mitigation plan. Sign-off from the Client must be obtained at this stage before proceeding with the release deployment.

Release testing involves testing for service operations readiness which ensures that a service and its underlying application, technology and infrastructure can be transferred into the production environment in a controlled manner (repeatable for subsequent deployments if required). It also ensures that business processes, Customers, Users and Service Provider interfaces are capable of using the service properly.